Skip to content

chore: remove references to Play gRPC from docs#650

Closed
He-Pin wants to merge 1 commit intoapache:mainfrom
He-Pin:port/3-remove-play-grpc-docs
Closed

chore: remove references to Play gRPC from docs#650
He-Pin wants to merge 1 commit intoapache:mainfrom
He-Pin:port/3-remove-play-grpc-docs

Conversation

@He-Pin
Copy link
Member

@He-Pin He-Pin commented Mar 8, 2026

Motivation

Documentation for Pekko gRPC contained references to the Play gRPC project (play-grpc), a separate independent project that is not part of Pekko gRPC. These references may confuse users or imply integration support that does not exist in this project.

Modification

  • Removed the "Play Framework support" section from docs/src/main/paradox/buildtools/gradle.md
  • Removed the [Play Framework](...) reference from the supported build tools list in docs/src/main/paradox/overview.md

Result

Documentation now focuses solely on Pekko gRPC's own supported build tools (sbt, Gradle, Maven) without referring users to an unrelated external project.

References

Port upstream akka/akka-grpc@8aa142b8.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@pjfanning
Copy link
Member

I'm not convinced that we need this. I have no issue with linking to Play gRPC as a related project. We can update our docs to say that it a related project as opposed to being a Pekko project but I'm not sure if we really need to go into that much detail.

@He-Pin
Copy link
Member Author

He-Pin commented Mar 8, 2026

Yes, that's why we need to check it manuly

@He-Pin He-Pin closed this Mar 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants